Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

How sessions start

Here is what happens when you start a Progress Dynamics session:

The Configuration File Manager is launched and initializes the session. The Configuration File Manager is a persistent procedure that determines and establishes the startup environment. It gets its session startup information from the Progress Dynamics configuration file (by default, icfconfig.xml).
Note: The Progress Dynamics upgrade process can overwrite the default file, icfconfig.xml. You should save a copy of your file before upgrading.

The icfconfig.xml file defines the environment in which Progress Dynamics can run. The definition of each session type includes the following startup information:

Its logical and physical resources (session services).
Its startup parameters (session properties).
The management procedures (Progress Dynamics managers) with which it runs.
Note: The Progress Dynamics configuration file can reside at a central source, anywhere on a network that can host an XML file, on behalf of all Progress Dynamics installations that rely on it. You can also import any manual changes that you make to the configuration file so all of its startup information is synchronized with and secure in the Repository. For more information, see the "Importing a configuration file" section.

For more information about the configuration file, see Appendix C "Inside the Progress Dynamics Configuration File."

The Connection Manager launches to manage the connections to required services, including databases, AppServer, Web services, and JMS Server (for SonicMQ connections only).

The Connection Manager calls a Service Type Manager that manages the physical connections for all session services of the same service type. Each service type has its own Service Type Manager. All Service Type Managers are built with a common starting API to the Connection Manager, allowing it the flexibility to handle any device or service that can be manipulated through that common API.

The Session Manager controls the operation of the application.
The Progress Dynamics session runs until you shut it down, or until it times out (if the session has a time-out setting specified for it). The Session Manager handles the termination of the session. First, it shuts down all persistent procedures that are running, then it shuts itself down.